I think an useful information in that table would be if the metric can be computed for each file or has to take the whole project into account.

I think an useful information in that table would be if the metric can be computed for each file or has to take the whole project into account.

That's a good idea! We could add a column that states the granularity of each metric.
I think we could follow this from QA: https://www.qa-systems.com/tools/qa-misra/metrics-and-visualisations/

Additional information regarding the HIS metrics as defined by the consortium (v1.3.1 - last open specification version).
HIS Source Code Metrics.pdf

@josecm @miguelafsilva5 Changed the base script for the HIS metrics to give more flexibility to the script:

• -f, --files option expects a list of files to be processed (e.g., -f /path/to/src1.c /path/to/hdr1.c)
• --{metric} options can be used to redefine a default value of the threshold for a specific metric (e.g., --level 200)
• -e, --exclude can be used to exclude a specific metric from the processing (e.g., -e level)

To try this locally use as e.g.: ./his_checker.py -f src/params/params.c --level 200 -e stmt.